Feature: RV32I progbuf-based memory access support #2185
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Detailed description
Tested on BMDA and blackpill-f411ce against GD32VF103.
Initial version used DATA0 DM MMR access from progbuf, second version is GPR-only. This is 2x slower than AAM on GD32VF103 (which is implements), but
Hart has 4 data registers and 2 progbuf registersso I intend to also implement the auto-incrementing snippets mentioned in Spec using abstractauto[0] (retrigger on DM DATA0 reads/writes).Your checklist for this pull request
Closing issues